ultra reliable low latency connection support in radio access networks

专利摘要:
Methods and systems are described in which a eu may establish and maintain a data link to a plurality of radio access nodes for the creation of redundant data links. Implementation methods for packet duplication as well as methods for determining when to enable or disable packet duplication are also disclosed.
公开号:BR112019006345A2
申请号:R112019006345
申请日:2017-09-29
公开日:2019-08-20
发明作者:Rao Jaya；Vrzic Sophie
申请人:Huawei Tech Co Ltd；
IPC主号:

专利说明:

ULTRACUSTIBLE LOW LATENCY CONNECTION SUPPORT IN RADIO ACCESS NETWORKS
CROSS REFERENCE FOR RELATED APPLICATIONS [001] This application claims priority benefit for US patent application 62 / 402,710 entitled Ultra Reliable Low Latency Connection Support in Radio Access Networks filed on September 30, 2016, US patent application 62 / 443,152 entitled Ultra Reliable Low Latency Connection Support in Radio Access Networks filed on January 6, 2017, US patent application 62 / 469,708 titled Ultra Reliable Low Latency Connection Support in Radio Access Networks filed on March 10, 2017 and for application US patent 15 / 718,394 entitled ULTRA RELIABLE LOW LATENCY CONNECTION SUPPORT IN RADIO ACCESS NETWORKS filed on September 28, 2017, the contents of which are incorporated into this document by reference in its entirety.
TECHNICAL FIELD [002] The present invention relates to ultra-reliable and low-latency connections in Radio Access Networks.
BACKGROUND [003] In a mobile communications network, a User Equipment (UE) connects to the network through the Radio Access Network, and more specifically through a radio access link to a Radio Access Node , such as a NodeB, an evolved NodeB (eNodeB) or other equivalent node including a gNóB. Transmissions between the UE and a node on the network typically involve at least one wireless channel between a Radio Access Node and the UE. Typically there are connections to
Petition 870190077206, of 08/09/2019, p. 7/73
2/53 additional wires between the radio access node and other nodes in the radio access network or a main network. Mobile networks have historically been designed to support the mobility of an UE (however mobility is not required in an UE). To maintain the connection between the UE and the network as the UE moves, transfer procedures have been developed to allow a session of the UE to be preserved as the radio access link travels between one access node and another . This process is known as a transfer.
[004] When developing transfer procedures, the interruption of a connection with an UE as the UE is transferred from one eNodeB to another is expected. This has an impact on the reliability of a connection. A human operator using the mobile network for a voice call may not notice the interruption, but a data session for critical tasks may not be as accommodating.
[005] The reliability of a connection is defined as a specified probability of successful transmission in a given time interval. For Ultra-Reliable Low Latency Connections (URLLC), a common reliability requirement is Ix10 ^-5 . This means that 99.999% of the transmitted packets must be received correctly within the latency requirement. The latency requirement may vary based on the needs of the service. It has been noted that there are now use cases in which LTE-based networks cannot provide connections that guarantee the latency required through real-time applications. In order to ensure reliability of the radio access channel, existing network designs, including Long Term Evolution standards
Petition 870190077206, of 08/09/2019, p. 8/73
3/53
(LTE) promulgated by the Third Generation Partnership Project (3GPP), make use of error correction mechanisms such as a Hybrid Automatic Repeat Request (HARQ). Although HARQ and other similar mechanisms can provide a degree of reliability, reliability can come with the cost of increased latency. If the latency requirement is 1 ms or less, then HARQ and Automatic Retry Request (ARQ) may not be adequate, as they can increase transmission latency.
[006] In order to provide both reliable and low latency connectivity, other techniques are required especially in mobility scenarios. In high-mobility scenarios or in very dense implementations, the number of cell-to-cell transfers to which a UE can be subjected can also adversely impact the ability to satisfy reliability and latency requirements.
[007] Therefore, there is a need for a system and method that at least partially address one or more limitations of the prior art.
[008] This prior information is provided to reveal information considered by the applicant to be of possible relevance to the present invention. No admission is not necessarily proposed, nor should it be interpreted that any preceding information constitutes prior art for the present invention.
SUMMARY [009] An objective of the present invention is to eliminate or mitigate at least one disadvantage of the prior art.
Petition 870190077206, of 08/09/2019, p. 9/73
4/53 [010] According to one aspect, a method of performing packet duplication (PD) on a transmitter is provided, comprising activating the PD on a packet Data Convergence Protocol (PDCP) layer of the transmitter; and duplicating a PDCP PDU in the PDCP layer, where the duplicated PDCP PDUs are transmitted to two RLC entities.
[011] According to an example, PD activation is applied in a dual connectivity (DC) / multiple connectivity (MC) architecture or in a carrier aggregation architecture (CA). According to another derived example, duplicate PDCP PDUs are assigned to different carriers. According to a third example, derived from the previous one, a PD function in the PDCP layer is responsible for duplication. According to a fourth example, derived from all the previous ones, the method additionally comprises deactivating the PD in the PDCP layer. According to a fifth example, derived from all the previous ones, MAC control elements (MAC CEs) are transported between the transmitter and a receiver to trigger an activation or deactivation of the PD. According to a sixth example, derived from all the previous ones, RRC signaling is received to configure the PD. According to a seventh example, derived from all of the above, RRC signaling is received to enable or disable the PD.
[012] According to another aspect, a processing system to perform packet duplication (PD) is provided, comprising: a first unit, configured to activate the PD in a Packet Data Convergence Protocol (PDCP) layer of the processing system; and a second unit, configured to duplicate a PDCP PDU in the
Petition 870190077206, of 08/09/2019, p. 10/73
5/53 PDCP layer, where duplicate PDCP PDUs are transmitted to two RLC entities.
[013] According to an example, PD activation is applied in a dual connectivity (DC) / multiple connectivity (MC) architecture or in an architecture (CA). According to a derived example, duplicate PDCP PDUs are assigned to different carriers. According to an additional example derived from those above, a second unit is a PD function in the PDCP layer responsible for duplication. A final example, derived from the previous one, includes a third unit, configured to disable the PD in the PDCP layer.
[014] According to a third aspect, a device is provided, comprising: the processing system according to any derivation of the previous aspect, and a fourth unit, configured to carry MAC control elements (MAC CEs) to trigger an activation or a deactivation of the PD.
[015] According to an example, the fourth unit is additionally configured to receive RRC signaling to configure the PD. According to another example, the fourth unit is additionally configured to receive RRC signaling to activate or deactivate the PD.
[016] The foregoing and other objectives, resources, aspects and advantages of the present invention will become more apparent with the detailed description below, considered together with the accompanying drawings, the description of which is by way of example only.
BRIEF DESCRIPTION OF THE DRAWINGS [017] For a more complete understanding of this revelation,
Petition 870190077206, of 08/09/2019, p. 11/73
6/53 reference is now made to the following short description, considered in connection with the accompanying drawings and detailed description, in which equal reference numbers represent equal parts.
[018] Figure 1 is an illustration of the timing problems resulting in the transfer interruption time of LTE networks according to a modality;
Figure 2 illustrates a logical view of the connection between a UE and a plurality of radio access nodes, according to a modality;
Figure 3 illustrates a transfer method, according to
with a modality; Figure 4 illustrates one method in to transmit data in redundant links, of a deal with an modality;Figure 5 illustrates one method in to transmit data in redundant links, of a deal with an modality;
Figure 6 illustrates a logical view of the connection between a UE and a plurality of radio access nodes, according to a modality;
Figure 7 illustrates a logical view of the connection between a UE and a plurality of radio access nodes, according to a modality;
Figure 8 illustrates the average Signal to Noise Ratio (SNR) of the original gNB Master (MgNB) and target MgNB during transfer, according to one modality.
Figure 9 illustrates a method of transfer procedure without interruption with diversity of RRC transmission and duplication of data to the source and target nodes, according to one modality;
Figure 10 illustrates an NR MC / DC Architecture for
Petition 870190077206, of 08/09/2019, p. 12/73
7/53 support PD, according to one modality;
Figure 11 illustrates an NR CA architecture to support PD, according to one modality;
Figure 12 illustrates sample message flows for an activation procedure triggered by Network, according to one modality;
Figure 13 illustrates example message flows for an LS / PD activation procedure triggered by UE, according to an embodiment;
Figure 14 illustrates an example Signaling flow to activate packet duplication, according to a modality;
Figure 15 illustrates an example signaling flow to disable packet duplication, according to a modality;
Figure 16 illustrates an example Signaling flow to enable and disable packet duplication based on criteria sent to the UE through RRC signaling, according to one modality; and
Figure 17 is a block diagram of a processing system that can be used to implement the various network functions and the methods and signaling as described in this document.
DETAILED DESCRIPTION [019] When discussing the provision of a service URLLC level, it should be understood that different levels of different networks need to be considered. Details of network layers, as well as details of service layers, need to be considered, as does session connectivity management. Although some of the details in each of these parts of a total solution overlap, a
Petition 870190077206, of 08/09/2019, p. 13/73
8/53 attempt will be made to deal with the details of one level at a time. As a result, the Figures can be introduced and discussed, and then discussed again as if they referred to a different layer in the solution.
[020] As noted earlier, the way in which transfer is achieved in an LTE network environment can result in delayed delivery (or dropped packets) during a transfer procedure. A UE is connected to a single eNodeB at a time. Driving in the direction of the transfer process, the UE is transmitting data for a single eNodeB, and the network is transmitting data for that same eNodeB of origin. However, as the UE connects to the target eNodeB, data that was sent to the source eNodeB before the transfer and that had not been delivered is not immediately present in the target eNodeB for delivery. This, as noted above, should probably not be apparent to a human operator on a voice call, or even seeing a video stream that has been temporarily stored locally. However, real-time processes, including real-time video sessions and certain control processes, are probably not as complacent.
[021] In order to reduce the likelihood of Radio Link Failure (RLF) during mobility, improvements to the transfer procedure can be provided. One way to achieve transfer without interruption is to ensure that there is at least one Radio Access Network (RAN) node connected to the UE at all times. Downlink (DL) data can be made available to the target RAN node prior to a transfer of the radio link. For
Petition 870190077206, of 08/09/2019, p. 14/73
9/53 Uplink Link (UL) communication, the target RAN node must have the path to the main network configured before a transfer of the radio link. This allows both UL and DL communications to be supported during a transfer from the source RAN node to the target RAN node, which reduces the likelihood of RLF.
[022] If the UE is at the edge of the service area of a source RAN node, initiating a transfer to the target node too soon may result in an RLF from the target node. Similarly, if a transfer is initiated too late then an RLF can occur at the originating node. In order to reduce the likelihood of packet loss or delay associated with the transfer procedure and to reduce the likelihood of RLF, simultaneous communication with both source and target RAN nodes can be provided for UEs near the edge.
[023] The timing diagram in Figure 1 shows the difference in the transfer procedure between LTE and a proposed new radio (NR) technology. In conventional techniques, as shown by the LTE 1 process, after the transfer command (HO) 10 is issued, there is a transfer interruption time. In this window, transmissions with the UE are interrupted. By allowing the UE to connect to a plurality of different access nodes, as illustrated in the NR 2 process, there is a time period 45 in which the UE is connected to more than one access node. This ensures that there is no interruption time (and effectively replaces the interruption time with a period in which simultaneous transmission 45 can be provided).
[024] This redundant transmission provides resilience to the possibility of link failure. It can also
Petition 870190077206, of 08/09/2019, p. 15/73
10/53 reduce any delays that would have been attributable to temporary storage by either end of the connection at the end of the transfer interruption.
[025] In the transfer scenario where duplicate UE packets are received on both the source and target nodes, the duplicates can be removed i) in the PDCP function of the target MgNB or ii) in the upper layers. That is, packets arriving within a latency limit from the source MgNB to the target MgNB via Xn can be detected and removed by the PDCP function on the target MgNB. Packets that can potentially exceed the latency limit at Xn are forwarded directly by both the source and target MgNB nodes to be detected and removed in the upper layers. It should be understood that MgNB refers to a master gNB.
[026] In order to ensure transfer without interruption of MgNB, a connection transfer procedure before disconnection can be used. For URLLC use cases, the UE can establish connectivity to the target MgNB before releasing the RRC connection to the source MgNB to allow duplication of packets through both MgNBs during a mobility event.
[027] During a normal transfer of UE connectivity from the source MgNB to a target MgNB, the UE may have only one link available for communication (data and RRC signaling), since the UE is required to release the MgNB RRC connection from source before establishing a new RRC connection to the target MgNB. In this case, the target reliability cannot be satisfied with a single link. Consequently, simultaneous data transmission and RRC signaling with links to both source and target MgNBs throughout the transfer
Petition 870190077206, of 08/09/2019, p. 16/73
11/53 will ensure greater reliability.
[028] According to an example, during the Simultaneous Transmission period 45 the UE is connected to more than one access node (for example, the Origin gNB and the Target gNB). During the Simultaneous Transmission period 45, Target Data Transmissions 30 include duplicate packets for those loaded during the Simultaneous Transmission period 45 by the Source 15 Data Transmission. In other words, during the Simultaneous Transmission period 45, Transmissions from Target Data 30 is a redundant transmission for that of Target Data Transmissions 30. To avoid interference, Target Data Transmissions 30 use a different channel (or equivalent to a different carrier) than the Source 15 Data Transmission.
[029] Again, according to an example, the transfer interruption time can be a window 20, and can persist until transfer is complete 25. The interruption window 20 can separate the Data Transmission signal from the Source 15 and the Target 30 Data Transmissions signal. The UE may establish RRC Connection for Target 40 during the Source 15 Data Transmission signal. Target 30 Data Transmissions can begin before the end of the Source 15 Data Transmission. .
[030] It should be noted that the examples were discussed with reference to MgNB nodes, but other properly equipped network access nodes can also be used, including a base station (for example, a NodeB, an evolved NodeB (eNodeB, or eNB ), a next generation NodeB (sometimes referred to as a gNóB or gNB)), or a Unit
Petition 870190077206, of 08/09/2019, p. 17/73
12/53 Base Band (BBU) associated with one or more remote radio heads.
[031] The benefits of using packet duplication also reveal benefits of using simultaneous radio connections during a transfer. Figure 8 illustrates the average SNR 67 0 of the source MgNB and the target MgNB during a transfer.
[032] The dependent variable axis of the graph illustrated by Figure 8 is SNR and the independent variable axis of this graph is Time / Distance 675. Figure 8 graphs the SNR curves for MgNB of Origin 590 and SNR for MgNB Target 595 , as well as the Region where packet duplication is required 650. The Time / Distance to Establish RRC Connection to Target 655 MgNB, Release RRC Connection to Origin MgNB 665 and the Time / Distance when Simultaneous Radio Connections 660 should exist between the UE and a plurality of NAs are also illustrated in Figure 8.
[033] Conditions during transfer are similar to channel conditions for scenarios that show a large gain for using packet duplication. During a transfer from the source MgNB, the average delta SNR between the source MgNB and the target MgNB is small and the average SNR for the best link is typically low. It can be concluded that packet duplication can be used during transfer using simultaneous radio connections to the source and target nodes. With packet duplication, target reliability can be achieved using less total resources.
[034] Multiple connectivity (MC), the ability of the network to support a plurality of different connection paths, can help satisfy the demand for
Petition 870190077206, of 08/09/2019, p. 18/73
13/53 reliability. By ensuring that an UE always has at least two paths to the CN, such as during a transfer, there is a reduced likelihood that the UE connection will be disconnected or broken. In the multiple connectivity scenario, the UE can be connected to multiple access nodes on the same carrier or on different carriers.
[035] LTE provides rudimentary dual connectivity (DC) functionality. To provide multiple connectivity, network elements can be designed to extend this DC concept into LTE. The 3C architecture option defined by 3GPP can be used, where there is a common PDCP entity.
[036] In an MC scenario (which may include a DC scenario) a radio access node is designated as a primary radio access node. Data packets can be sent to a secondary RAN node (via the primary radio access node) on an Xn interface. Uplink link packets can be received by any of the RAN nodes to which the UE is connected. Each of the secondary RAN nodes then sends the received packets to the primary RAN node via the Xn interface.
[037] Figure 2 illustrates a NR protocol stack, where gNB refers to an access node.
[038] The primary gNB (gNB-1 200) acts as an anchor or MgNB for this connection. If a new gNB (gNB-2 250) has to be added, the primary gNB will create a new Xn 112 link for the additional gNB. The PDCP layer 106 on the Anchor node can be used to remove duplicate packets that are received from multiple RAN nodes communicating with the UE 100. The UE may be allowed to move through multiple distributed RAN nodes connected to the same Anchor node without having to re-establish the security association with the PDCP layer
Petition 870190077206, of 08/09/2019, p. 19/73
14/53
106. When the UE 100 moves out of a coverage area associated with the anchor RAN node, the UE can establish the security association with the PDCP function on the target RAN node. Alternatively, the main network can initiate the key exchange during the mobility event.
[039] In order to ensure transfer of the Anchor node function from a first gNB to a second gNB, a connection transfer procedure before disconnection can be used. The UE 100 can establish a radio connection to the target Anchor node before releasing the RRC connection from the source Anchor node. Therefore, the UE 100 will have two simultaneous radio connections during a mobility event with only one RRC connection to the originating RAN node. An exemplary procedure using simultaneous radio connections is illustrated in Figure 11. It should be understood that SgNB refers to a Secondary gNB.
[040] In the transfer procedure, when the transfer condition is met, the originating MgNB sends an RRC connection reconfiguration to establish a radio carrier for the target MgNB. In this case, the UE maintains a radio connection and RRC connection with the originating MgNB. After the RB for the target node is established, packet duplication can be used for both data and RRC signaling.
[041] According to an example modality of the transfer procedure in Figure 2, the UE 100 is configured with the two protocol stack entities 101, 102 so that UE 100 can communicate simultaneously with two access points (for example, example, gNBs 200, 250). The UE 101 protocol stack entity includes the NR-RLC 110 entity, the NR-MAC 115 entity and the
Petition 870190077206, of 08/09/2019, p. 20/73
15/53 entity NR-PHY 120. The EU protocol stack entity
102 includes an NR-RLC 111 entity, the NR-MAC 141 entity and the NR-PHY 142 entity. Both EU 101 protocol stacks, 102 share a common NR-PDCP 105 entity. The primary gNB protocol stack entity 103 (gNB-1 200) includes an NR-PDCP 106 entity, the NR-RLC 114 entity, the NR-MAC 115 entity and the NR-PHY 120 entity. protocols 104 of the second gNB (gNB-2 250) includes the NR-RLC 113 entity, the NR-MAC 115 entity and the NRPHY 120 entity, but does not require its own PDCP entity. The protocol stack entity 104 of the gNB-2 250 communicates with the NR-PDCP 106 of the gNB-1 200 via the Xn 112 interface. The EU protocol stack entity 102 including the NR-RLC 111 entity, the entity NR-MAC 115 and entity NRPHY 120 communicate with the protocol stack entity
103 of the primary gNB (gNB-1 200) using a first radio channel 116. The EU protocol stack entity 101 including the NR-RLC 110 entity, the NR-MAC 115 entity and the NR-PHY 120 entity communicate with the protocol stack entity 104 of the secondary gNB (gNB-2 250) using a second radio channel 117.
[042] It should be noted that, as an example, the protocol stack entity 104 of the second gNB (gNB-2 250) may include a PDCP entity, but a PDCP entity like this is disabled or not used in this example when another RAN node is acting as a master or anchor node. Therefore, when the UE moves outside the range of its anchor gNB (for example, gNB-1 200), another gNB (for example, gNB-2 250) is configured as the new anchor RAN node, activating its entity PDCP. It should also be noted that, although only
Petition 870190077206, of 08/09/2019, p. 21/73
16/53 secondary RAN node is illustrated in Figure 2, there may be additional secondary access nodes.
[043] Another example procedure is illustrated in Figure 3, using simultaneous radio connections, according to a modality.
[044] Figure 3 illustrates the transfer procedure after the RRC connection and a path to transfer data between the UE 100 and the Origin 300 gNB have been established (through Establish RRC Connection 400 and Data signals 405). When the transfer condition is met (via the Criteria for transferring without interruption procedure 410), the source gNB 300 sends an RRC connection reconfiguration to establish a radio carrier (RB) for the target gNB (as illustrated by the Request signal) secondary RRC connection to target 415) for UE 100. In some embodiments this enables packet duplication (PD) to ensure that PDUs are not lost during transfer. In this case, the UE 100 maintains a radio connection and RRC connection with the source gNB 300. After the RB for the target node is established, as illustrated by the sign Establish another RRC 420 connection passed between the UE 100 and the gNB target 340, packet duplication can be used for both data and RRC signaling. In this embodiment, packet duplication includes transmitting duplicate packets between UE 100 and the Origin 300 gNB via the Data 425 signal and between UE 100 and the target gNB 340 via the Data 430 signal.
[045] When the condition to release the RRC connection with the source node is met, the source node (and optionally the target node) sends an RRC connection reset command
Petition 870190077206, of 08/09/2019, p. 22/73
17/53 to complete the RRC connection to the target node. The radio link with the originating node is maintained. Once the RRC connection is established to the target node, the UE can disconnect the radio connection to the originating node.
[046] This is illustrated by the Criteria process for releasing origin satisfied 435. The Separation Command 440 sent by the Origin gNB 300 to the UE 100 causes the UE 100 to perform the Separate process from the Origin gNB 445. In some modalities this may trigger deactivation PD if PD is not required at all times for the session.
[047] In some embodiments, the UE sends duplicate packets to a plurality of access nodes. Each of the access nodes sends the received packets to the PDCP function of the primary access node (which may involve transmission on an Xn interface, or on another such interface). In the DL direction, the PDCP function on the primary node generates duplicate packets and forwards the packets to the secondary node / nodes through an Xn interface. The UE removes any duplicate packets received.
[048] The redundant transmission provided by the redundant connection can further reduce the delay by eliminating the reordering delay in the RLC and PDCP layers. In URLLC modalities where ARQ and HARQ are not used, reordering in the RLC and PDCP layers may not be necessary. Similarly, RLC reordering may not be necessary. Although an RLC entity may have lost PDUs, in an MC architecture, there is an increased probability that a PDU that would otherwise be lost will be received by at least one of the radio nodes. This results in a reduced probability that each RLC will lose the same PDU. Such
Petition 870190077206, of 08/09/2019, p. 23/73
18/53 as noted, modalities of the proposed invention may provide for the elimination, or reduction in the amount, of necessary reordering if ARQ and HARQ are not employed in the presence of multiple redundant packages.
[049] Figure 4 illustrates an exemplary embodiment of a URLLC transmission. Duplicate UL packets in this mode are removed by the anchor RAN node, while the UE 100 removes duplicate DL packets. For UL transmission, the UE 100 transmits packets to each of a plurality of access nodes. As a result, a single packet can be received by more than one access node. All received packets are routed through the plurality of AN nodes received to a single RAN node (the anchor RAN node gNB-1 200), typically via the Xn 112 interface as noted earlier. Only the anchor RAN node gNB-1 200 needs to implement a PDCP function for this connection. The packets received by the anchor node (both through the air interface and through the Xn 112 interface) are forwarded to the PDCP 106 function. The PDCP 106 function of the Anchor node removes duplicate packets resulting from the redundant connection. In DL transmissions, the PDCP 105 function in UE 101 can be used to consider duplicate packets received as a result of redundant transmissions from the plurality of access nodes. Each of the secondary access nodes receives packets for redundant transmission over the Xn 112 interface from the primary access node.
[050] Therefore, PDCP included in the gNB-1 200 can duplicate packets and pass them to both gNB-2 250 and UE 100 (illustrated by the Duplicate packets and send to multiple AN 470 nodes and DL Data signals) 475 and 480).
Petition 870190077206, of 08/09/2019, p. 24/73
19/53
UE 100 also includes a PDCP 105 that performs the Remove Duplicate Packets 485 process to remove duplicate packets received from both gNB-1 200 and gNB-2 250. Again, in some embodiments, it does not matter whether it is the original PDU or the duplicate PDCP PDCP that is removed (for example, deleted).
[051] According to an example of the modality in Figure 4, the anchor RAN node is gNB-2 250). In an example of the same modality the UE 100 transmits packets to each of a plurality of access nodes as illustrated by the Duplicate packets and send to multiple AN 450 nodes process and by the UL 455 and 460 Data signals. process 450 includes producing a duplicate PDU (referred to as a duplicate PDCP PDU), which is performed by NR-PDCP 105 in Figure 2. The packets duplicated by NR-PDCP 105 are transmitted simultaneously to gNB-1 200 and gNB2 250 through the two entities of protocol stacks NR 101, 102 of the UE and more specifically by the NR-RLC entities
110, 111, NR-MAC 115, 141 and NR-PHY 120, 142. Therefore, the PDCP 105 layer duplicates packets, and delivers an original PDCP PDU through a first RLC 110 entity, first MAC 115 entity and first PHY entity 120 and delivers a duplicate PDCP PDU via a second RLC 111 entity, second MAC 141 entity and second PHY 142 entity. For example, the EU protocol stack entity 101 (includes the NR-RLC 110 entity, the NR entity -MAC 115 and the NR-PHY 120 entity) transmits an original PDCP PDU via communication channel 117 to gNB-2 250. Similarly, the EU protocol stack entity 102 (includes an NR-RLC entity
111, the NR-MAC 141 entity and the NR-PHY 142 entity) transmit
Petition 870190077206, of 08/09/2019, p. 25/73
20/53 a duplicated PDCP PDU for gNB-1 200 via communication channel 116.
[052] According to another example of the modality in Figure 4, the PDCP 106 function of the Anchor node removes duplicate packets resulting from the redundant connection as illustrated by the Remove Duplicate Packets 465 process. In some modalities, it doesn't matter if it is the PDU original or the duplicated PDCP PDU that is removed (for example, deleted).
[053] Removing duplicate packages is illustrated by Removing duplicate packages in the 465 sample process. In some embodiments, it does not matter whether it is the original PDU or the duplicate PDCP PDU that is removed (for example, deleted).
[054] It will be realized that the method and system proposed above can make use of simultaneous transmissions in a plurality of redundant links. This can be used to reduce the likelihood of RLF and to increase the reliability of the connection. These redundant links can be created using a multiple connection architecture, of which a double connection architecture can be understood as a special case. The PDCP function can be centralized on the primary RAN node and the UE. Secondary RAN nodes can receive downlink packets from the primary RAN node via the Xn interface, and can provide upstream link packets received to the primary RAN node via the Xn interface without applying PDCP functions. PDCP functions can be used to detect and address duplicate packets.
[055] Issues related to the provision of redundant connectivity, as presented above, will now be discussed from the perspective of the network layer.
Petition 870190077206, of 08/09/2019, p. 26/73
21/53 [056] In a system that allows MC / DC, a UE will connect to a RAN node, for service. As the UE moves, it can connect to a second RAN node. The first RAN node will be considered the source RAN node. As the UE approaches a second RAN node (referred to as a target RAN node), it can connect to the target RAN node, while still communicating with the current server (source) RAN node. To reduce the delay associated with transfer, at least one of the following requirements must be addressed:
- The target RAN node can be provided with context information about the UE (and its connections) before the UE establishes a connection to the target RAN node. This allows a reduction in the transfer delay that would otherwise be caused by the UE needing to establish context information with the target RAN node;
- Connections to the main network (CN) for both UL and DL traffic can be established by the target RAN node before (or not later than the time of) establishing the connection with the UE;
- Downlink traffic destined for the UE can be made available to both the current server RAN node and the target RAN node.
[057] While the factors discussed above may reduce the likelihood of packet delay or loss of connection to the UE, it should also be understood that other factors may contribute to the reliability required for a URLLC connection. Such factors may include a requirement for redundant links, both radio links and links in the network infrastructure. Such redundant links can be provided using different RAN nodes, some of which
Petition 870190077206, of 08/09/2019, p. 27/73
22/53 which can employ a different Radio Access Technology (RAT). In cases, the redundant connection can make use of the DC / MC architecture described above. This can allow UL and DL transmissions to use a plurality of different transmit / receive points. Another factor may include support for a seamless transfer. Transfer support without interruption in the network can help ensure that the UE has access to a connection to the network with limited or no service interruption during a transition from one radio link to another. Transfers between cells without interruption can also help to ensure that packets are not lost or delayed when switching from one radio access link to another.
[058] Multiple connectivity can be used to help satisfy reliability requirements by ensuring that an UE always has at least two paths to the CN. In the multiple connectivity scenario, the UE can be connected to multiple access nodes on the same carrier or on different carriers. In some cases, different access nodes may be using different RATs (for example, LTE and NR). Dual connectivity can make use of different generations of radio access link connections (for example, an LTE or HSPA) along with next generation radio access technology (for example, RAT 5G) that can make use of radio connections different frequencies (for example, below 6 GHz or millimeter wave connections). For example, connections of different frequencies can be used to support multiple RATs.
[059] Multiple connectivities can be enabled through an extension of the existing DC concept in LTE. The option
Petition 870190077206, of 08/09/2019, p. 28/73
23/53 3C architecture can be used, where there is a common PDCP entity such as, for example, the gNB-1 200 illustrated in Figure 2. Because of initial next generation implementations (such as a so-called 5G network ) may not have uniform coverage, connectivity through multiple RATs (for example, NR and LTE) allows for earlier support of a URLLC service without having to wait for an implementation that covers a complete geographic area. The transmission of data through multiple RATs must take into account the different options for working implementations together. For example, a next generation radio (NR) technology can operate autonomously or it can be supported by an LTE node. A node of either generation can be used as the anchor node. In the case of multiple RATs, the server RAN nodes may contain transmit and receive points (TRPs) from both RATs.
[060] As shown in Figure 5, a UE 350 can communicate with a next generation NodeB (gNodeB, or gNB), through an interface indicated as NR-Uu 137, which is analogous to the Uu 127 interface for an eNB LTE. An Xn 112 interface is used to connect the primary RAN node (gNB 200) to a secondary RAN node (eNB 370). Similar to the previous discussion in relation to Figure 2, the Xn interface allows downstream link traffic to be pushed to the target RAN node, and for UL traffic received by the target RAN node to be pushed to the primary RAN node. PDCP functions can be implemented in the UE and the primary RAN node (illustrated here as gNB 200). Those skilled in the art will understand that additional secondary nodes can be connected, each having an Xn interface to the primary RAN node.
Petition 870190077206, of 08/09/2019, p. 29/73
24/53 [061] The PDCP layer 105 on the primary RAN node / anchor can be used to remove duplicate UL packets received from the UE 350 through the plurality of radio links. The UE 350 can travel through the combined service areas of the plurality of target RAN nodes, each connected to the same Anchor node. In some modalities, the connection can be changed between the connected RAN nodes without having to re-establish the security association with the PDCP layer. When the UE moves outside the cover of the anchor RAN node, the UE can establish the security association with the PDCP function on the target RAN node. Alternatively, the main network can initiate the key exchange during the mobility event.
[062] The UE 350 uses two layer stacks when connected simultaneously to both NR RANs and LTE RANs. The layer stack used by the UE 350 to connect to the LTE RAN eNB 370 includes layers RLC 125, MAC 130 and PHY 135. This capability for simultaneous connection to two different Radio Access Technologies (RATs) enables support for multiple Technologies Radio Access (multiple RATs). The layer stack used by the UE 350 to connect to the NR RAN gNB 200 includes layers NR-RLC 110, NR-MAC 115 and NR-PHY 120. Both of these layer stacks in this mode share an NR-PDCP 105 layer. The gNB 200 in this layer stack of the modality includes layers NR-PDCP 106, NR-RLC 114, NR-MAC 143 and NR-PHY 144. eNB 370 in this layer stack of the modality includes layers RLC 156, MAC 157 and PHY 158.
[063] UL and DL transmissions in a URLLC scenario are illustrated in Figure 6. As can be seen, the UE sends duplicate packets to a plurality of access nodes.
Petition 870190077206, of 08/09/2019, p. 30/73
25/53
Each of the access nodes sends the received packets to the PDCP function of the primary access node (which may involve transmission via an Xn interface, or another such interface). In the DL direction, the PDCP function on the primary node generates intentional duplicate packets when forwarding packets to the secondary node / nodes through an Xn interface. The UE removes any duplicate packets received.
[064] Figure 6 illustrates a modality where the UE 100 connects to an LTE eNB 320 as well as gNB 310 and Anchor node 330 to illustrate the UE's ability to connect simultaneously to both NR RANs and LTE RANs. Thus, Figure 6 illustrates a modality that allows simultaneous connection to two different Radio Access Technologies (RATs), however it must be realized that this is an example of multiple Radio Access Technologies (multiple RATs). The UE 100 duplicates packets and sends them to both gNB 310 and eNB 320 using the Duplicate packets and send to multiple AN 490 nodes and UL 495 and 500 data signals. Each access node sends the received packets for the PDCP function of the Anchor node 330 (which may involve transmission via an Xn interface, or another such interface). Therefore, gNB 310 then passes this data to Anchor 330 via the UL 505 Data signal, which can be via an Xn interface. It should be noted that, in some modalities, gNB 310 can act as the anchor node, in which case signal 505 represents internal signaling between entities. ENB 320 also passes the same data to Anchor 330 via the UL 510 Data signal (which can be via an Xn Interface). Anchor 330 includes a PDCP function configured to remove duplicate UL packets that it receives
Petition 870190077206, of 08/09/2019, p. 31/73
26/53 when executing the Remove Duplicate Packets 515 process. Anchor 330 also duplicates DL packets and sends them to both of the eNB 320 and gNB 310 through the Duplicate packets and send to multiple AN 520 nodes and DL Data signals 525 and 530, which can be via an Xn interface. ENB 320 sends DL data it receives from Anchor 330 to UE 100 via DL 540 data signal. GNB 310 also sends DL data it receives from Anchor 330 to UE 100 via DL 535 data. UE 100 removes DL data duplicates he receives from eNB 320 and gNB 310 when executing the Remove Duplicate Packets 545 process.
[065] In order to ensure seamless transfer of Anchor node responsibilities, a connection transfer procedure before disconnection can be used. The UE can establish a radio connection to the target Anchor node before releasing the RRC connection from the source Anchor node. Therefore, the UE will have two simultaneous radio connections during a mobility event, but there is an RRC connection with the originating node. The transfer procedure using simultaneous radio connections is illustrated in Figure 9.
[066] In the transfer procedure, when the condition for transfer is satisfied, the source MgNB 360 sends an RRC connection reconfiguration to establish a radio carrier for the target MgNB. In this case, the UE 100 maintains a radio connection and RRC connection with the source MgNB 360. After the RB for target node 365 is established, packet duplication can be used for both data and RRC signaling.
[067] When the condition to release the RRC connection with the originating node is satisfied, the originating node (and optionally
Petition 870190077206, of 08/09/2019, p. 32/73
27/53 the target node) sends an RRC connection reset command to complete the RRC connection to the target node. The radio link with the originating node is maintained. Once the RRC connection is established to the target node, the UE can disconnect the radio connection to the originating node.
[068] The redundant links, used in the method and system described above, can be achieved through the use of MC (of which DC can be seen as a special case). In a configuration like this, RAN nodes can be configured to use a common PDCP entity. The PDCP function for transmitting RAN nodes can support packet duplication for a multiple connectivity architecture. The PDCP functions on the primary RAN node and the UE can be assigned responsibilities for handling packet duplication. During mobility, the UE can be provided with a plurality of simultaneous radio connections to both source and target RAN nodes to allow for a reduction in the likelihood of service interruption in transfers between cells. In this case, the UE maintains a single RRC connection.
[069] According to an example, the procedure can start after the RRC connection has been established (Establish RRC Connection 400 and Data 405 signals) between UE 100 and Source 360 MgNB. It should be noted that the procedure for transfer, duplication of packages and release of origin, according to the modality illustrated in Figure 9, is an alternative to the modality illustrated in Figure 3.
[070] According to an additional example, there is a process Criteria for transfer without interruption satisfied 410 provided optionally to satisfy the condition of
Petition 870190077206, of 08/09/2019, p. 33/73
28/53 transfer. The destination of the RRC connection reconfiguration to establish a radio carrier can be the UE 100 via the RRC Connection Reconfiguration signal (establish RB only) 550. Target node 365 can be established using the Establish Radio Carrier 555 signal. For packet duplication, data can be transmitted between UE 100 and Source 360 MgNB via Data 560 signal and between UE 100 and Target 365 MgNB via Data 565 signal.
[071] Again, for example, the condition for releasing the RRC connection to the originating node can be satisfied through the procedure Criteria for releasing originating satisfied 570. The originating node can signal this via the RRC Connection Reconfiguration signal (complete RRC connection for target) 575 and target node using the Complete RRC Connection for MgNB Target 580 signal. The UE can disconnect the radio connection to the source node using the Separate MgNB process from source.
[072] Figure 7 illustrates a modality in which a Radio Access Node 602 is shown operating as a secondary node 605 for a primary node 600, and also operating as a primary node 610 for another secondary node 615. As will be understood, each primary node can have a plurality of secondary nodes, and a structure like this as illustrated in Figure 7 allows for a tree-like structure when modeling the relationship between nodes.
[073] In order to achieve better resource utilization and improve spectral efficiency by supporting packet duplication (PD), the various diversity techniques supported in LTE and 5G (new radio (NR)) architectures can be explored and improved. These architectural techniques
Petition 870190077206, of 08/09/2019, p. 34/73
29/53 include:
- Multiple connectivity / Dual connectivity (MC / DC): Operating mode where the UE is able to access radio resources provided by at least two different network access nodes (for example, Master and Secondary gNBs) that are connected via non-ideal return traffic (ie, Xn interface). In one example, the network access nodes can be the same Master and Secondary gNBs or different Radio Access Technologies (RATs).
- Carrier Aggregation (CA): Operation mode where multiple component carriers (CCs) can be used together in both frequency division duplex (FDD) and time division duplex (TDD) transmission modes to achieve high rates of data. In this architecture, multiple small cells can be configured with different carriers. The small cells are connected to the macrocell with optimal return traffic.
[074] Improvements that can be made to the MC / DC and CA architectures to support PD techniques will be discussed below.
[075] First, improvements that can be made to MC / DC architectures to support PD techniques will be discussed, according to various modalities. The MC / DC architecture includes the master and secondary gNBs (MgNB 600, 610 and SgNB 605, 615) connected via the Xn 250, 112 interfaces. While the MgNB 600 hosts the total RAN protocol stack (composed of the PDCP 105 layers , RLC 114, MAC 143 and PHY 144), SgNB 615 hosts only the lower layers (i.e., RLC 125, MAC 130 and PHY 135). Also, each MgNB can support multiple links / cells, consisting of one
Petition 870190077206, of 08/09/2019, p. 35/73
30/53
Primary Cell (PCell) and several Secondary Cells (SCells). Collectively, the cells / links controlled by MgNB form the Macrocell Group (MCG). The SgNB, in turn, supports and controls the Secondary Cell Group (SCG) including a Small Primary Cell (PSCell) and several SCells.
[07 6] It should be noted that primary RAN node 600 supports an Xn 250 interface to communicate with secondary RAN node 605. Secondary RAN node 605 hosts the lower layers that include NR-RLC 145, NR-MAC 150 and NR -PHY 155. The primary RAN pseudo node 610 hosts the stack of total RAN protocols including NR-PDCP 625 along with the lower layers that include NR-RLC 145, NR-MAC 150 and NR-PHY 155. It is noted that in illustrated mode the lower layers including NR-RLC 145, NR-MAC 150 and NR-PHY 155 are shared between primary RAN pseudonó 610 and secondary RAN node 605, but it should be noted that separate RLC, MAC and PHY entities can be used.
[077] The RRC 700 entity, hosted on MgNB 362, will be responsible for configuring all protocol layers for both MgNB 362 and SgNB 367, as shown in Figure 10. Figure 10 illustrates an example NR MC / DC Architecture to support PD, according to a modality. To support PD, an objective is to configure and assign each duplicated protocol data unit (PDU) to a different set of links / cells in MgNB 362 and SgNBs 367 to achieve maximum diversity. In another modality, the MC / DC Architecture may include other RATs. For example, it can include NR in combination with LTE or eLTE.
[078] In an MC / DC architecture like this, the PDCP entity
Petition 870190077206, of 08/09/2019, p. 36/73
31/53
706 at the transmitter hosts a new Packet Duplication (PD) function that duplicates PDCP PDUs. Each instance of the duplicated PDUs can carry the same PDCP sequence number (SN). At the receiver, the PDCP entity hosts a PD removal function that can perform a combination of the received PDCP PDUs (for example, using a bit level soft combination technique).
[07 9] The radio carrier for logical channel mapping between PDCP and RLC can be configured to be one to one in such a way that additional duplication is not required in the RLC 711 layer. The RLC can be configured (by RRC 700) to operate in unrecognized mode (UM) or transparent mode (TM) when PD in PDCP is activated.
[080] In each access node (ie, MgNB 362 and SgNB 367) in MC / DC, the logical channels in the MAC layer 705 can be mapped to a transport channel associated with a different link / cell / carrier. In this case, the mapping between each logical channel to the transport channel is also set to one to one. There may be a common scheduler / multiplexer in the upper MAC layer (UMAC 705) that can perform cross-carrier scaling of MAC PDUs or transport blocks (TBs) over a different link / cell / carrier. In the lower MAC layer (L-MAC 710), each link in turn can be handled by its own HARQ process which can be configured to support a certain maximum number of retransmissions (for example, 1 retransmission per HARQ process). This allows the HARQ processes (for each link) to operate independently of each other.
[081] In the PHY 715 layer, each transport channel can
Petition 870190077206, of 08/09/2019, p. 37/73
32/53 be handled by its own PHY 715 entity, enabling a different number of physical resource blocks (PRBs) and modulation and coding schemes (MCS) to be configurable in both downlink (DL) and link link transmissions. climb (UL).
[082] Improvements that can be made to the CA architecture to support PD techniques will be discussed, according to various modalities. Figure 11 illustrates an example NR CA Architecture to support PD, according to one modality. The CA architecture includes a stand-alone access node that can include a full RAN protocol stack with the ability to support transmissions across multiple CCs. The CCs, in turn, can include a Primary Cell (PCell) and several Secondary Cells (SCells). To support PD, each duplicate package can be assigned to a different DC. Also in CA, the duplication function can be hosted in the PDCP entity or in the MAC entity.
[083] In the case where PD is performed on PDCP 706, a similar operation can be implemented as previously described in relation to the MC / DC architecture. In some embodiments, if PD is executed at the MAC 705 layer, each received MAC service data unit (SDU) (from RLC 711) can be duplicated for multiple MAC PDUs (ie multiple transport blocks (TBs) of the same size ). Here, in contrast to the case of duplication in the PDCP, the mapping between each logical channel to transport channel is 1 for many. Therefore, the RRC 700 can configure the MAC layer to ensure that each transport channel is mapped to a different DC.
[084] On U-MAC 705, there may be a
Petition 870190077206, of 08/09/2019, p. 38/73
33/53 common scheduler / multiplexer that can perform cross-carrier scaling of MAC PDUs between different CCs. There may also be a common HARQ entity that can function across different CCs while supporting common HARQ temporary storage. On the L-MAC 710, each DC can be associated with its own HARQ process, which can be configured to handle a certain maximum number of retransmissions. The data received in each HARQ process can be stored in the common temporary storage managed by the common HARQ entity. The HARQ ACK / NACK feedback in each HARQ process can be controlled by the common HARQ entity. At the receiver, soft combining technique can be used to perform combination of the received packets through different HARQ processes in the common HARQ entity. In addition, the soft combination on the receiver removes duplicates and the resulting PDU is routed to the upper layers (ie, RLC 711 and PDCP 706).
[085] The following table is a Summary of Impacts
Architectural to support PD, according to modalities.
CA impacts forsupport PD MC / DC impacts to support PD RRC RRC can configure CCs for packet duplication. SCells are added / removed based on UL control information (UCI). RRC can configure MgNB and SgNBs for PD. SgNBs are added / removed based on UCI and / or measurements from neighboring cells. PDCP No impact unless duplication of It consists of a new PD function that is responsible for
Petition 870190077206, of 08/09/2019, p. 39/73
34/53
packets to run in PDCP. If PD is executed in PDCP then a new PD function is required. duplicate PDCP PDUs in Tx and remove duplicate PDUs received (through a combination technique) in Rx. RLC No impact. ARQ is No impact. ARQ isconfigured in UM mode configured in UM mode oror TM by default in TM by default in both ofboth from MgNB and SgNB. MgNB and SgNB. MAC Consist of U-MAC In DL, onecommon (scheduler, scheduler / multiplexerHARQ entity) and common can performmultiple L-MAC (for carrier escalationeach DC). In DL, crossover of MAC SDUscommon scheduler received from layersperforms duplication of higher. Each MAC PDU isMAC SDUs received from designated for CCsupper layers. (PDSCH). At theEach duplicate PDU is receiver, the CC PDUdesignated for CCs different (PUSCH) notmany different. At the needs to be combined.receiver, the PDUs of HARQ process in each CCDifferent CCs are can standcombined by soft. retransmissions butEach CC can allow through CC-HARQretransmission to HARQ management is notHARQ. A common HARQ entity can manage all CC-HARQ processes. required.
Petition 870190077206, of 08/09/2019, p. 40/73
35/53
For UL Tx, the UE is designated with multiple concessions UL in CCs many different for PD. 0 receiver in gNB can run combination by soft across CCs.PHY No impact No impact
[086] Activation techniques to support Duplication of Packets will now be discussed according to several modalities.
[087] In the initial access procedure (ie RRC Connection Establishment procedure) the UE is able to provide its capacity information to PCell (ie MgNB) indicating the number of CCs and Tx / Rx chains ( to access SgNBs) that it can support. The UE can specifically indicate your preference for cross-band CA configuration and the reliability requirement to support URLLC.
[088] Based on specified capacity, the RRC entity configures PCell and several SCells in the MCG to support URLLC transmissions. Optionally, the RRC can also configure a set of SCGs, consisting of PSCell and SCells in the SgNBs, as part of the RRC Connection Reconfiguration procedure. In the event that the PSCell in the SgNB is configured, the configuration parameters are transmitted by MgNB via RRC containers (as part of the SgNB Add / Change request procedure) via the Xn interface. New SgNBs can be added to the existing SCG pool and existing SgNBs can be added
Petition 870190077206, of 08/09/2019, p. 41/73
36/53 updated or released through the RRC Connection Reconfiguration procedure in the event that the UE is mobile. After the initial access procedure, the following options can be applied as a trigger mechanism to activate / deactivate PD mode.
[089] Activation for packet duplication and link selection will now be discussed according to several modalities.
[090] As an alternative to PD, Link Selection (LS) techniques according to modalities can achieve reliability by selecting and provisioning the best available transmission link based on fast channel measurements. This is based on the assumption that there is a coverage region on the network with highly favorable channel conditions (eg high SNR with line of sight (LOS), low load) where transmitting on a single best link is sufficient to satisfy the requirements URLLC. Outside of this region, PD approaches as discussed in this document are used to satisfy URLLC requirements.
[091] In this regard, a triggering mechanism can be applied to switch between LS and PD modes based on a selection criterion that can be implemented in the network or in UE as described below.
[092] First, a network-driven approach will be discussed according to modalities. An LS / PD activation procedure triggered by an example network is illustrated in Figure 12, according to one modality. In the network-triggered approach, MgNB 370 initially activates the PCell and deactivates the SCells within the set of links / CCs configured by the RRC. The link / CC activation / deactivation status can be transported to the UE 100 through the
Petition 870190077206, of 08/09/2019, p. 42/73
37/53 MAC control elements (MAC CEs). Note that, in the case of MC / DC, the set of links used for PD can include those of both MGC (MgNB) and SGC (SgNB).
[093] The MgNB 370 can also request UE 100 channel quality information (CQI) reports on all links / CCs activated via a DL control information signal (DCI). UE 100 transmits CQI reports through the UCI. If temporary storage of PDCP / RLC data is not empty, the UE 100 can also transmit the escalation request (SR) at the UCI.
[094] Based on channel measurements and total load information, MgNB 370 can use a trigger criterion to determine the best transmission mode for the UE 100. That is, the selection of LS or PD is performed when selecting the best k CCs (or links) among the n available CCs, where when k = 1 LS is selected and when k> 1 PD is selected. As an example, the steps involved in the triggering criteria can be listed as follows:
i) If the CQI and the resources available on the best link are sufficient to satisfy the reliability requirement, MgNB 370 selects the LS mode.
ii) If the CQI and the resources available on the best link are not sufficient to satisfy the reliability requirement then MgNB 370 considers the second best link to select the PD mode. The second best link must satisfy the following criteria: i) the CQI of the second best link is above a CQI_limiar, ii) the delta_CQI of the best link and the second best link are below a delta_limiar and iii) the resources available in the second best link are above a resource threshold.
Petition 870190077206, of 08/09/2019, p. 43/73
38/53 iii) If the two best links are not enough to satisfy the reliability requirement then MgNB 370 also considers the third best link. The third best link must also satisfy the requirements previously indicated for CQI_limiar, delta_limiar and resource_limiar.
iv) This procedure is repeated until the reliability requirement is satisfied or there are no more links (cells / carriers).
[095] In the case where LS is selected, MgNB 370 selects an activated link / DC and sends a DCI, to designate DL resources or to grant UL resources for a single transmission.
[096] If PD is selected, MgNB 370 selects multiple activated links / CCs and sends a DCI for each selected link / DC. A new DCI format can be used to indicate that the UL grant is used for PD. The new packet duplication field can be a single bit to identify which leases are used for PD.
[097] Alternatively, the packet duplication field can be a sequence number, which identifies the leases that are used for specific PD transmissions.
[098] In another mode, a single UL grant can be sent to the UE, which indicates the cells / carriers to be used for PD.
[099] Based on the selected mode, MgNB allocates resources on the activated link (s) / DC (s) and indicates the resource configuration (for example, PRBs, MCS, antenna ports) for the UE in the DCI. MgNB can also provide UL leases and enables semi-permanent scheduling (SPS) configuration via
Petition 870190077206, of 08/09/2019, p. 44/73
39/53 of the DCI.
[0100] At UL, the UE transmits data on UL shared physical channel (PUSCH) while continuing to report the CQI on all activated CCs (on UL control physical channel (PUCCH)). Subsequent transmissions may include ο Temporary Storage Status (BSR) reporting on MAC CE.
[0101] In the DL, data is transmitted over the staggered DC / link (s) in the DL shared physical channel (PDSCH).
[0102] MgNB can update the set of configured links / DCs that can be indicated to the UE through the RRC Connection Reconfiguration procedure.
[0103] As an example, during the process, UE 100 and MgNB 370 exchange the RRC Connection Reset information via signal 375, UE Capacity Information via signal 380 and RRC Connection Reconfiguration (Pcell and Scell Configuration) via signal 385.
[0104] The triggering criteria can be exemplified using the LS / PD 395 Shooting Criteria process. During this process the UE 100 and MgNB 370 exchange the LS / PD Shooting information (MAC CE) via signal 800, UL Concessions ( PDCCH) via signal 805 and Data URLLC and UCI (PUCCH, PUSCH) via signal 810.
[0105] According to an example, process reports can be sent on the physical UL control channel (PUCCH) through the UCI signal (CQI of configured CCs) 390.
[0106] According to an additional example, the DCI can be sent via URRLC and DCI data signal (PDSCH, PDCCH) 815.
[0107] An EU-led approach will now be
Petition 870190077206, of 08/09/2019, p. 45/73
40/53 discussed according to modalities. An LS / PD activation procedure triggered by an example UE is illustrated in Figure 13, according to one embodiment. Similar to the case triggered by the network, in the case triggered by the UE 100 the MgNB 370 activates a set of links / CCs for the UE 100 to perform channel measurements. All links / CCs, except for PCell, are initially set to be in the default deactivated state. However, in contrast to the case triggered by the network, MgNB can pre-allocate certain resources on the configured links while still keeping the links in a disabled state. MgNB can also provide resource configuration (for example, PRBs, MCS potential range) in conjunction with UL grants through DCI. In addition, the UL grant for each link may contain a validity timer, indicating the duration for which the resources on the corresponding links are valid and reserved for the UE.
[0108] Based on the availability of data in the PDCP / RLC buffer and the measured channel conditions, the UE can apply a criterion to determine the trigger to select the PD mode. As an example, the steps involved in the triggering criteria for LS / PD are listed as follows:
i) If the CQI of the best link is sufficient to satisfy the reliability requirement, the UE selects the LS mode.
ii) If the CQI of the best link is not sufficient to satisfy the reliability requirement then the UE considers the second best link to select the PD mode. The second best link must meet the following criteria: i) the
Petition 870190077206, of 08/09/2019, p. 46/73
41/53
CQI of the second best link is above a CQI_limiar, ii) the delta_CQI of the best link and the second best link are below a delta_limiar.
iii) If the two best links are not enough to satisfy the reliability requirement then the UE also considers the third best link. The third best link must also satisfy the requirements indicated above for CQI_limiar and delta_limiar.
iv) This procedure is repeated until the reliability requirement is satisfied or there are no more links (cells / carriers).
[0109] In UL, the UE 100 transmits data in the PUSCH. In the DL, data is transmitted in links (cells / CCs) staggered in PDSCH.
[0110] Additionally, it must be possible for MgNB to invalidate the selection capacity triggered by UE dynamically when sending an indicator in the PDCCH to limit the use of free concession resources for the primary / carrier cell. This indicator can be a single bit to indicate whether or not the UE uses PD in the grant-free resources in the different cells / carriers. The PD indicator can be signaled dynamically or semi-statically.
[0111] Alternatively, there may be a PD indicator for the resources free of concession in each cell / carrier. The UE can only use the concession-free resources in the cells / carriers where the PD indicator is established.
[0112] In another mode, RRC signaling can be used to configure PD in the concession-free resources in multiple cells / carriers.
Petition 870190077206, of 08/09/2019, p. 47/73
42/53 [0113] Signaling for Duplication of Packets will now be discussed, according to modalities. The criteria for enabling and disabling packet duplication depends on the DL and UL channel conditions as well as loading on different cells / carriers. In both DC / MC and CA architectures, MgNB (PCell) makes the decision as to whether or not to enable packet duplication for the UE.
[0114] Once packet duplication is activated, MgNB can dynamically decide how many links (cells) are used to transmit both DL and UL to satisfy the required reliability. The UE may receive one or more DL designations or UL grants for the transmission of a packet.
[0115] The number of links that are used for UL and DL may be different. This is because the loading on UL and DL can be significantly different.
[0116] The network can also provide the UE with criteria for determining when to use packet duplication, while the UE is configured for packet duplication. This allows the UE to decide when to use packet duplication.
[0117] Pre-allocation described above is in accordance with the concession-free technique where resources are pre-allocated to UEs without going through the dynamic scheduling procedure involving scheduling request (SR) sent by the UE and subsequent allocation of resources. As an example, MgNB 370 informs UE 100 of the UL concession through the sign UL Concessions for pre-allocated resources in configured CCs (PDCCH) 805. During this process, MgNB 370 and UE 100 also exchange information Restoration RRC connection via signal
Petition 870190077206, of 08/09/2019, p. 48/73
43/53
375, Information Capacity from EU via 380 signal and Connection Reset RRC (Configuration from Pcell and Scell) via signal 385 • [0118] According with implementations of example, O trigger criteria can to be satisfied by the process
Shooting Criteria LS / PD 395). In addition, data can be transmitted in UL using the Data URLLC (PUSCH), MAC CE (PS / PD Trigger), UCI (CQI reports) 820 signal and the Data URLLC and DCI (PDSCH, PDCCH) 815 signal in DL.
[0119] Figure 14 illustrates an example signaling flow to activate duplication of packages, according to modalities. In this procedure, new cells / carriers can be added to the UE 100 based on the measurement reports from the UE. The MgNB server can use link selection to determine the best cell / carrier to send the packets. If the criteria for enabling packet duplication (PD) 865 are met then the MgNB server 370 sends an RRC 870 connection reconfiguration message to activate the PD mode. Once the UE 100 sends the RRC Complete 875 Reconfiguration message, the packet duplication mode can be activated. This means that the UE can receive multiple messages from DL designations and multiple UL grants for the same URLLC packet. Use of link selection can be via Data 855 passed between UE 100 and MgNB 370 and Data 860 passed between UE 100 and SgNB 830.
[0120] UE 100 sends Measurements DL (SgNB) 835 to MgNB 370, MgNB 370 and p SgNB 830 exchange the information Add PScell 840, and MgNB 370 transmits the message
Petition 870190077206, of 08/09/2019, p. 49/73
44/53
Reconfiguration of RRC Connection (add SgNB) 845. A radio bearer 850 is also established between UE 100 and SgNB 830. Once PD has been configured for a Data Radio Bearer (DRB), MAC 100 controls elements to enable or disable PD. Duplicate packets are sent between UE 100 and MgNB 370 via Data 560 and between UE 100 and SgNB 830 via Data 565.
[0121] Figure 15 illustrates an example signaling flow to disable packet duplication, according to modalities. In this procedure, if the UE 100 is in PD mode, the MgNB server 370 evaluates the criteria for disabling PD based on the UE channel measurements and the load on the cells / carriers. If the PD criteria are met, the MgNB 370 sends an RRC 871 Connection Reset message to disable the PD mode. Once the UE 100 sends the Complete RRC Reconfiguration message 876, the PD mode can be disabled and the MgNB server can use link selection to transmit the packets.
[0122] The link selection process involves sharing Data 855 between UE 100 and MgNB 370 and Data 860 between UE 100 and SgNB 830. According to an example, duplicate packets flow between UE 100 and the MgNB 370 via signal 560 and between UE 100 and SgNB 830 via signal 565. Evaluation of the criteria to disable PD can be via process 866. Channel measurements can be received from UE 100 via MgNB 370 via signal DL measurements (SgNB ) 835).
[0123] In some scenarios, MgNB may provide the UE with criteria for enabling / disabling packet duplication. The UE evaluates the criteria to determine when to use packet duplication. Figure 16 illustrates flow of
Petition 870190077206, of 08/09/2019, p. 50/73
45/53
Example signaling to activate and deactivate packet duplication based on criteria sent to the UE 100 by means of RRC signaling, according to modalities. In this procedure, the MgNB 370 sends an RRC 873 Connection Reset message to configure the UE 100 with the PD activation criteria. In this case, the UE 100 is also configured with features that can be used for packet duplication (for example, free-of-charge features in multiple cells / carriers).
[0124] In some modalities, the same signaling to activate / deactivate packet duplication can be applied in both DC / MC and CA architectures.
[0125] In some modalities, RRC signaling can be used to configure the packet duplication mode for the UE.
[0126] In some embodiments, the criteria for enabling and disabling packet duplication may depend on the DL and UL channel conditions as well as cell loading.
[0127] In some embodiments, the decision to use duplicate packets for UL and DL can be determined independently.
[0128] In some embodiments, the decision to use packet duplication, while the UE is in packet duplication mode, can be made over the network. In other words, even if the UE is in packet duplication mode, the network can invalidate the decision.
[0129] In some modalities, the network may provide the UE with criteria to determine when to activate / deactivate packet duplication. The UE uses the criteria to take the decision
Petition 870190077206, of 08/09/2019, p. 51/73
46/53 decision on when to use packet duplication.
[0130] It should be noted that the methods described above can be implemented using controllers on the various devices (for example, UE 100, MgNB 370, SgNB 830, etc.). Therefore, several modalities include a controller including a processor and machine-readable instructions that, when executed by the processor, induce the device to implement the methods and signaling described previously.
[0131] Some of the listed modalities can be considered as examples of the criteria for activating PD 880 and the criteria for deactivating PD 885.
[0132] According to an example, the UE 100 informs the MgNB 370 that it has completed this configuration via the RRC Complete Reset 875 message. Since the UE determines that the criteria for activating PD (based on criteria provided in RRC signaling) 880 are satisfied, the UE switches to PD mode. At that point, duplicate packets flow between the UE 100 and the MgNB 370 via Data 560 and between the UE 100 and the SgNB 830 via Data 565. Since the UE determines that the criteria for disabling PD (based on criteria provided in signaling RRC) are satisfied 885, the UE disables the PD mode. At that point Link selection data is passed between UE 100 and MgNB 370 via signal 855 and between UE 100 and SgNB 830 via signal 860.
[0133] Figure 17 is a block diagram of a 1001 processing system that can be used to implement the various network functions and the methods and signaling as previously described, according to modalities. As shown in Figure 17, processing system 1001 includes
Petition 870190077206, of 08/09/2019, p. 52/73
47/53 a processor 1010, working memory 1020, non-transitory storage 1030, network interface 1050, input / output interface 1040 and, depending on the type of node, a transceiver 1060, all of which are communicatively coupled via 1070 bidirectional bus.
[0134] According to certain modalities, all the elements represented can be used, or only a subset of the elements. In addition, processing system 1001 can contain multiple instances of certain elements, such as multiple processors, memories or transceivers. Also, elements of the 1001 processing system can be coupled directly to other components without the bidirectional bus.
[0135] The memory can include any type of non-transitory memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), any combination of these or something like that. The mass storage element can include any type of non-transitory storage device, such as a solid state drive, hard disk drive, a magnetic disk drive, an optical disk drive, USB drive, or any program product computer configured to store machine executable program code and data. According to certain modalities, the memory or mass storage has statements and instructions executable by the processor to execute the functions and steps mentioned above. Processing system 1001 can be used to implement a UE or host that performs the various network and UE functions
Petition 870190077206, of 08/09/2019, p. 53/73
48/53 described in this document. In one example, the host in this document can be a RAN node.
[0136] Through the descriptions of the preceding modalities, the present disclosure can be implemented by using only hardware or by using software and a necessary universal hardware platform. Based on such understandings, the technical solution of the present disclosure can be incorporated in the form of a software product. The software product can be stored on non-volatile or non-transitory storage media, which can include device memory as described above, or stored in removable memory such as compact disc read-only memory (CD-ROM) , flash memory or a removable hard drive. The software product includes several instructions that enable a computing device (computer, server or network device) to perform the methods provided in the modalities of this disclosure. For example, an execution like this can correspond to a simulation of the logical operations as described in this document. The software product may additionally or alternatively include several instructions that enable a computing device to perform operations to configure or program a digital logic device according to the modalities of the present disclosure.
[0137] Additional modalities of the present invention are provided in the following. It should be noted that the numbering used in the following section does not necessarily have to match the numbering used in the previous sections.
[0138] Modality 1. A method of transferring a
Petition 870190077206, of 08/09/2019, p. 54/73
49/53
User Equipment (UE) in a Radio Access Network, for execution by a source radio access node having a first Radio Resource Control (RRC) connection to the UE, the method comprising:
determine which criteria for a seamless transfer from the UE to a target radio access node are met;
transmitting to the UE an instruction to establish a second radio connection between the UE and the target radio access node while maintaining the radio and RRC connection with the source radio access node;
receiving, in response to the instruction for the UE to establish a radio connection, an indication that the second radio connection to the target radio access node is established; and transmitting an RRC connection reset command to the UE to move the RRC connection from the source RAN node to the target RAN node.
[0139] Mode 2. The method of mode 1 in which the step of determining which criteria for a seamless transfer are satisfied includes receiving measurement reports from the UE.
[0140] Mode 3. The method of any preceding mode in which the step of transmitting an instruction to the UE to establish a second radio connection includes transmitting an instruction to establish a second radio connection in parallel to the first radio connection it supports the RRC connection.
[0141] Mode 4. The method of any previous mode, additionally including the stage of transmitting
Petition 870190077206, of 08/09/2019, p. 55/73
50/53 data to the UE after transmitting the instruction to establish a second radio connection to the UE.
[0142] Mode 5. The method of any of modes 1 to 3 additionally including the step of transmitting data to the UE after receiving an indication that the second radio connection is established.
[0143] Modality 6. A method of transferring User Equipment from a first radio access node, with which a first Radio Resource Control (RRC) connection is established, to a second radio access node in a Radio Access Network, the method comprising:
transmitting to the first radio access node a signal measurement report indicative of the ability to connect to the second radio access node;
in response to receiving an instruction from the first radio access node, establish a second radio connection with the second radio access node;
transmit data to, or receive data from, the first and second Radio access nodes; and release the first RRC connection.
[0144] Mode 7. The method of mode 6 in which the data transmitted to or received from the first and second Radio access nodes are the same.
[0145] Mode 8. The method of any of modes 1 to 5 further comprising transmitting to the UE a separation command instructing the UE to release the first RRC connection.
[0146] Mode 9. The method of mode 8 in which to transmit a separation command to the UE is subsequent
Petition 870190077206, of 08/09/2019, p. 56/73
51/53 to transmit an RRC connection reconfiguration command to the UE.
[0147] Mode 10. Architectures as described.
[0148] Mode 11. A method of applying the same signaling to enable / disable packet duplication on both DC / MC and CA architectures.
[0149] Mode 12. A RRC signaling method used to configure the packet duplication mode for the UE.
[0150] Mode 13. A method for enabling and disabling packet duplication using criteria dependent on the DL and UL channel conditions as well as cell loading.
[0151] Mode 14. The method of mode 13 in which the decision to use packet duplication for UL and DL can be determined independently.
[0152] Mode 15. A method of deciding to implement duplication of packets determined by a UE.
[0153] Mode 16. The method of mode 15 in which the UE receives criteria to determine when to activate / deactivate packet duplication of a network node.
[0154] Mode 17. A method of deciding to implement packet duplication determined by a network node.
[0155] Mode 18. The method of mode 17 in which the network node can instruct a UE in packet duplication mode to change modes.
[0156] Mode 19. A method of transferring User Equipment (UE) over a Radio Access Network, for execution by a source radio access node having a first Radio Resource Control (RRC) connection
Petition 870190077206, of 08/09/2019, p. 57/73
52/53 for the UE, the method comprising:
receive measurement reports from the UE;
transmitting to the UE an instruction to establish a second radio connection between the UE and a target radio access node while maintaining the radio and RRC connection with the originating radio access node;
receiving, in response to the instruction for the UE to establish a radio connection, an indication that the second radio connection to the target radio access node is established; and transmitting an RRC connection reset command to the UE to move the RRC connection from the source RAN node to the target RAN node.
[0157] Mode 20. A method of a receiver, comprising:
activate the PD in a PDCP layer of the receiver; and removing duplicate PDCP PDUs in the PDCP layer, where duplicate PDCP PDUs are received from two RLC entities.
[0158] Mode 21. The method of mode 1, in which the activation of PD is applied in a dual connectivity (DC) / multiple connectivity (MC) architecture or in a CA architecture.
[0159] Mode 22. The method of mode 20 or 21, additionally comprising: deactivating the PD in the PDCP layer.
[0160] Mode 23. The method of any of the modes 20-22, in which MAC control elements (MAC CEs) can be transported between the receiver and a transmitter to trigger an activation or deactivation of the PD.
[0161] Mode 24. The method of any of the
Petition 870190077206, of 08/09/2019, p. 58/73
53/53 modalities 20-23, further comprising: transmitting RRC signaling to configure the PD in a PDCP PDU transmitter.
[0162] Mode 25. The method of any of the 20-24 modes, additionally comprising: transmitting RRC signaling to activate or deactivate the PD in a PDCP PDU transmitter.
[0163] Mode 26. The method of any of the modalities 20-25, in which a PD removal function in the PDCP layer performs a combination of the received PDCP PDUs.
[0164] Although the present disclosure has been described with reference to specific modalities and resources therein, it is evident that various modifications and combinations can be made to this without departing from the disclosure. The specification and drawings, therefore, should be considered simply as an illustration of examples of an invention defined by the appended claims, and are considered to cover any modifications, variations, combinations or equivalences that are within the scope of the present disclosure.

权利要求:
Claims (17)
[1]
AMENDED CLAIMS
1. Method of performing packet duplication (PD) on a transmitter, characterized by the fact that it comprises:
activate the PD in a Packet Data Convergence Protocol (PDCP) layer of the transmitter; and duplicating a PDCP PDU in the PDCP layer, where the duplicated PDCP PDUs are transmitted to two RLC entities.
[2]
2. Method, according to claim 1, characterized by the fact that PD activation is applied in a dual connectivity (DC) / multiple connectivity (MC) architecture or in a carrier aggregation architecture (CA).
[3]
3. Method, according to any previous claim, characterized by the fact that the duplicated PDCP PDUs are designated for different carriers.
[4]
4. Method, according to any previous claim, characterized by the fact that a PD function in the PDCP layer is responsible for duplication.
[5]
5. Method, according to any previous claim, characterized by the fact that it additionally comprises deactivating the PD in the PDCP layer.
[6]
6. Method, according to any previous claim, characterized by the fact that MAC control elements (MAC CEs) are transported between the transmitter and a receiver to trigger an activation or deactivation of the PD.
[7]
7. Method, according to any previous claim, characterized by the fact that it additionally comprises receiving RRC signaling to configure the PD.
[8]
8. Method, according to any previous claim, characterized by the fact that it additionally comprises
Petition 870190077179, of 08/09/2019, p. 7/10
2/3 receive RRC signaling to activate or deactivate the PD.
[9]
9. Processing system to perform packet duplication (PD), characterized by the fact that it comprises:
a first unit, configured to activate the PD in a Packet Data Convergence Protocol (PDCP) layer of the processing system; and a second unit, configured to duplicate a PDCP PDU in the PDCP layer, in which the duplicated PDCP PDUs are transmitted to two RLC entities.
[10]
10. Processing system, according to claim 9, characterized by the fact that PD activation is applied in a dual connectivity (DC) / multiple connectivity (MC) architecture or in a carrier aggregation architecture (CA) .
[11]
11. Processing system according to claim 9 or 10, characterized by the fact that the duplicated PDCP PDUs are designated for different carriers.
[12]
12. Processing system according to any one of claims 9 to 11, characterized in that a second unit is a PD function in the PDCP layer responsible for duplication.
[13]
13. Processing system according to any one of claims 9 to 12, characterized in that it additionally comprises:
a third unit, configured to disable PD at the PDCP layer.
[14]
14. Device, characterized by the fact that it comprises:
the processing system as defined in any
Petition 870190077179, of 08/09/2019, p. 8/10
3/3 one of claims 9 to 13, and a fourth unit, configured to carry MAC control elements (MAC CEs) to trigger an activation or deactivation of the PD.
[15]
15. Device, according to claim 14, characterized by the fact that the fourth unit is additionally configured to receive RRC signaling to configure the PD.
[16]
16. Device according to claim 14, characterized by the fact that the fourth unit is additionally configured to receive RRC signaling to activate or deactivate the PD.
[17]
17. Media readable by a non-transitory processor, characterized by the fact that it stores instructions that, when executed by one or more processors, induce the one or more processors to execute a method as defined in any of claims 1 to 8.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019006345A2|2019-08-20|ultra reliable low latency connection support in radio access networks

---

JP6904394B2|2021-07-14|Communications system

---

US11184942B2|2021-11-23|Operating with multiple schedulers in a wireless system

---

BR112019019804A2|2020-04-22|transmission of reliable data packet between entities in a radio access network of a mobile communication network

---

ES2821768T3|2021-04-27|Data transmission control in radio access networks

---

US9622132B2|2017-04-11|Switching between cellular and license-exempt | bands

---

TWI472201B|2015-02-01|Method of handling uplink timing and related communication device

---

US20170111923A1|2017-04-20|User equipments, base stations and methods for low latency radio communications

---

KR20200104425A|2020-09-03|Method and apparatus for enhancing cell-edge user performance and signaling radio link failure conditions via downlink cooperative component carriers

---

JP6257759B2|2018-01-10|System and method for improving radio link performance in a multi-carrier environment

---

CN110771082A|2020-02-07|System, apparatus and method for packet data convergence protocol packet data unit replication

---

US10080223B2|2018-09-18|Method for configuring transmission time interval bundling at a user equipment with multiple carriers and device therefor

---

BR112020026121A2|2021-03-16|WIRELESS TRANSMISSION / RECEPTION UNIT, AND, METHOD IMPLEMENTED IN A WIRELESS TRANSMISSION / RECEPTION UNIT

---

KR20160135766A|2016-11-28|Method and apparatus for improved multi-carrier communication

---

EP3737154A1|2020-11-11|User equipment and related method

---

CN110741722A|2020-01-31|Control mechanism for packet replication in multi-connection communication

---

BR112019019718A2|2020-04-14|method, and, wireless device.

---

CN112385303A|2021-02-19|Communication system and communication terminal device

---

JP6313905B2|2018-04-18|Base station and user equipment

---

US20210337627A1|2021-10-28|Packet generation and distribution method for supporting carrier aggregation between base stations, and device therefor

---

BR112020022170A2|2021-02-02|method for configuring user equipment, first centralized unit, and non-transitory, computer-readable media

---

CN113039733A|2021-06-25|Apparatus, method and computer program

---

TWI755581B|2022-02-21|Sul failure handling

---

US20220086947A1|2022-03-17|Operating with multiple schedulers in a wireless system

---

KR20120122903A|2012-11-07|Method of handling soft buffer for carrier aggregation and related communication device

同族专利:

---

公开号 | 公开日

---

EP3510799A1|2019-07-17|

---

CA3038849A1|2018-04-05|

---

CN109792658A|2019-05-21|

---

EP3510799A4|2019-07-17|

---

US20180098250A1|2018-04-05|

---

JP2019530355A|2019-10-17|

---

RU2019113138A3|2020-10-30|

---

KR102214429B1|2021-02-08|

---

KR20190055221A|2019-05-22|

---

RU2019113138A|2020-10-30|

---

US10750410B2|2020-08-18|

---

WO2018059557A1|2018-04-05|

---

EP3510799B1|2021-06-09|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US20030081582A1|2001-10-25|2003-05-01|Nikhil Jain|Aggregating multiple wireless communication channels for high data rate transfers|

---

TW200816700A|2006-09-29|2008-04-01|Interdigital Tech Corp|Method and apparatus of adaptive sequence numbering in a wireless communication system|

---

WO2009009532A2|2007-07-11|2009-01-15|Interdigital Technology Corporation|Packet data convergence protocol operations|

---

KR101669966B1|2009-05-11|2016-10-27|엘지전자 주식회사|Method for transmitting and receiving duplicated data in a multi-carrier supported wireless communication system and appratus for the same|

---

WO2011063244A2|2009-11-19|2011-05-26|Interdigital Patent Holdings, Inc.|Component carrier activation/deactivation in multi-carrier systems|

---

US9769842B2|2013-01-10|2017-09-19|Telefonaktiebolgaet LM Ericsson |Simultaneous uplink transmissions in dual connectivity mode|

---

CN104904254B|2013-01-11|2018-11-23|Lg 电子株式会社|Method and apparatus for sending information in a wireless communication system|

---

WO2014119921A1|2013-01-29|2014-08-07|Lg Electronics Inc.|Method and apparatus for transmitting indicator in wireless communication system|

---

US9392481B2|2013-03-15|2016-07-12|Futurewei Technologies, Inc.|System and method for buffer status reporting for multi-stream aggregation|

---

ES2769858T3|2013-04-01|2020-06-29|Innovative Sonic Corp|Method and apparatus for adding service cells in a wireless communication system|

---

US10362590B2|2013-09-26|2019-07-23|Kt Corporation|Method for transmitting uplink data and apparatus for same|

---

KR101475934B1|2013-07-02|2014-12-23|고려대학교 산학협력단|Mode controlling node and method thereof in an ad-hoc network|

---

BR112016002425A2|2013-08-09|2017-08-01|Ericsson Telefon Ab L M|method for handling subframe scheduling and subframe scheduling, and first and second base station|

---

EP2854444A1|2013-09-27|2015-04-01|Panasonic Intellectual Property Corporation of America|Efficient uplink scheduling mechanism for dual connectivity|

---

WO2015047051A1|2013-09-30|2015-04-02|Lg Electronics Inc.|Method for determining radio resource control configuration in wireless communication system supporting dual connectivity and apparatus thereof|

---

EP3061309B1|2013-10-21|2020-04-08|LG Electronics Inc.|Method and ue for transmitting uplink data in a dual connectivity and a device therefor|

---

WO2015060860A1|2013-10-25|2015-04-30|Telefonaktiebolaget L M Ericsson |Rrc diversity|

---

US10433176B2|2013-11-11|2019-10-01|Telefonaktiebolaget Lm Ericsson |Discarding a duplicate protocol data unit associated with a data transmission via a first signaling radio bearer or a second signaling radio bearer|

---

CN110932835A|2014-01-29|2020-03-27|北京三星通信技术研究有限公司|Method and device for processing activation/deactivation of carrier aggregation between base stations|

---

ES2838678T3|2014-05-08|2021-07-02|Ntt Docomo Inc|User equipment, radio base station, radio communication method and radio communication system|

---

US9749098B2|2014-05-09|2017-08-29|Electronics And Telecommunications Research Institute|Method and apparatus for transmitting and receiving system information in mobile communication system|

---

JP5852193B1|2014-08-06|2016-02-03|株式会社Ｎｔｔドコモ|User equipment|

---

US10142799B2|2014-08-19|2018-11-27|Qualcomm Incorporated|Multicasting traffic using multi-connectivity|

---

US9628586B2|2014-08-29|2017-04-18|Lg Electronics Inc.|PDCP operation in a wireless communication system supporting dual connectivity|

---

US10750410B2|2016-09-30|2020-08-18|Huawei Technologies Co., Ltd.|Ultra reliable low latency connection support in radio access networks|

---

CN107979847B|2016-10-25|2020-12-15|华为技术有限公司|Data transmission method, device, user equipment and base station|

---

EP3535878A1|2016-11-04|2019-09-11|Telefonaktiebolaget LM Ericsson |Activation and deactivation of duplication transmission|

---

CN110856189B|2017-01-05|2020-11-10|华为技术有限公司|Data transmission method and device|

---

US10716094B2|2017-03-23|2020-07-14|Ofinno, Llc|Packet duplication in a wireless device and wireless network|

---

US10536878B2|2017-03-24|2020-01-14|Mediatek Inc.|User equipment and methods for PDCP duplication in 5G RAN|

---

WO2018184503A1|2017-04-02|2018-10-11|Wei, Chia-Hung|Logical channel data packet transmission method and wireless communication system|

---

US10405231B2|2017-04-24|2019-09-03|Motorola Mobility Llc|Switching between packet duplication operating modes|

---

KR20190139886A|2017-04-24|2019-12-18|모토로라 모빌리티 엘엘씨|Replication of PDCP PDUs for Radio Bearer|

---

TWI665897B|2017-04-26|2019-07-11|華碩電腦股份有限公司|Method and apparatus for requesting resource for control element transmission in a wireless communication system|

---

US10805836B2|2017-05-05|2020-10-13|Qualcomm Incorporated|Packet duplication at a packet data convergence protocol entity|

---

EP3399724A1|2017-05-05|2018-11-07|ASUSTek Computer Inc.|Method and apparatus of transmitting data duplication in a wireless communication system|

---

US11212701B2|2017-05-14|2021-12-28|FG Innovation Company Limited|Systems, methods, and devices for ultra-reliable low latency communication quality-of-service guarantee|

---

CN112616161A|2017-06-15|2021-04-06|华为技术有限公司|Communication processing method and communication device|

---

EP3923499A1|2017-06-15|2021-12-15|Samsung Electronics Co., Ltd.|Packet duplication control|

---

US20180368107A1|2017-06-15|2018-12-20|Alireza Babaei|Logical Channel Mapping With Packet Duplication|

---

CN107979647B|2017-12-07|2020-10-23|合肥国为电子有限公司|Data recovery method for realizing cable-free storage type seismograph|US10750410B2|2016-09-30|2020-08-18|Huawei Technologies Co., Ltd.|Ultra reliable low latency connection support in radio access networks|

---

CN109845321B|2016-10-11|2021-12-07|瑞典爱立信有限公司|Data transmission during handover|

---

CN107979847B|2016-10-25|2020-12-15|华为技术有限公司|Data transmission method, device, user equipment and base station|

---

KR20180050015A|2016-11-04|2018-05-14|삼성전자주식회사|Method and apparatus for data transmission and reception of ultra reliable and low latency communications in wireless communication system|

---

EP3554166A4|2017-01-13|2020-08-12|Samsung Electronics Co., Ltd.|Method and device for transmitting data packet in wireless communication system|

---

CN109417723A|2017-02-02|2019-03-01|Lg电子株式会社|Method and apparatus for sending data cell|

---

DK3579608T3|2017-03-03|2021-06-07|Guangdong Oppo Mobile Telecommunications Corp Ltd|DATA TRANSMISSION METHOD AND DEVICE|

---

EP3585093B1|2017-03-23|2021-09-01|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Method for transmitting data, terminal device, and network device|

---

WO2018184503A1|2017-04-02|2018-10-11|Wei, Chia-Hung|Logical channel data packet transmission method and wireless communication system|

---

US11228940B2|2017-04-27|2022-01-18|Mitsubishi Electric Corporation|Communication system|

---

CN108811129B|2017-05-05|2020-03-10|华为技术有限公司|Resource scheduling method and equipment|

---

US10448289B2|2017-05-05|2019-10-15|Futurewei Technologies, Inc.|System and method for handovers in a dual connectivity communications system|

---

CN112615702A|2017-05-05|2021-04-06|中兴通讯股份有限公司|Control method and device for data packet replication function and communication equipment|

---

WO2018221926A1|2017-06-02|2018-12-06|Lg Electronics Inc.|Apparatus and method for performing packet duplication|

---

EP3923499A1|2017-06-15|2021-12-15|Samsung Electronics Co., Ltd.|Packet duplication control|

---

US20180368107A1|2017-06-15|2018-12-20|Alireza Babaei|Logical Channel Mapping With Packet Duplication|

---

US20180367288A1|2017-06-16|2018-12-20|Huawei Technologies Co., Ltd.|Dynamic activation and deactivation of packet duplication|

---

US10659381B2|2017-06-16|2020-05-19|Mediatek Singapore Pte. Ltd.|Method and apparatus for handling data duplication in mobile communications|

---

EP3422767A1|2017-06-26|2019-01-02|Panasonic Intellectual Property Corporation of America|User equipment and base station participating in packet duplication during handover for nr|

---

MX2019015149A|2017-07-25|2020-02-19|Guangdong Oppo Mobile Telecommunications Corp Ltd|Switching method, access network device and terminal device.|

---

EP3661090A4|2017-07-28|2021-03-10|Fujitsu Limited|Command instruction method and device, and information interaction method and device|

---

WO2019030431A1|2017-08-09|2019-02-14|Nokia Technologies Oy|High reliable low latency data transmission using grant-less uplink transmission format on scheduled pusch resources|

---

US20190200273A1|2017-12-22|2019-06-27|Nokia Technologies Oy|Flushing PDCP Packets To Reduce Network Load In Multi-Connectivity Scenarios|

---

CN110691424B|2018-01-12|2020-09-18|华为技术有限公司|Communication processing method and device for repetitive mode under CU-DUarchitecture|

---

CN110710143B|2018-02-08|2021-01-12|Oppo广东移动通信有限公司|Method and terminal equipment for processing Radio Link Failure |

---

US10687263B2|2018-02-15|2020-06-16|Qualcomm Incorporated|Enhanced make-before-break handover|

---

EP3782434A4|2018-04-20|2021-12-08|ZTE Corporation|Apparatus and method for mobility management|

---

US10834661B2|2018-04-27|2020-11-10|Qualcomm Incorporated|Multiple connectivity for high reliability|

---

US10582507B2|2018-05-17|2020-03-03|At&T Intellectual Property I, L.P.|Network coding for bandwidth efficient reliability improvement for URLLC service|

---

CN110621075A|2018-06-20|2019-12-27|华为技术有限公司|Method and device for transmitting data|

---

US11071100B2|2018-07-06|2021-07-20|Qualcomm Incorporated|Techniques and apparatuses for transmitting downlink control informationon a physical downlink shared channel |

---

WO2020010191A1|2018-07-06|2020-01-09|Qualcomm Incorporated|Techniques and apparatuses for transmitting downlink control informationon a physical downlink shared channel |

---

US10972950B2|2018-07-20|2021-04-06|Qualcomm Incorporated|Methods and apparatus for handover enhancements|

---

CN110784904A|2018-07-31|2020-02-11|夏普株式会社|Access control method and user equipment|

---

US20210297899A1|2018-08-01|2021-09-23|Samsung Electronics Co., Ltd.|Method and device for controlling duplicate packet transmission in wireless communication system|

---

CN110798408B|2018-08-02|2021-04-20|华为技术有限公司|Message transmission method and device|

---

CN110831169A|2018-08-09|2020-02-21|华为技术有限公司|Method and equipment for configuring carrier|

---

EP3834330A1|2018-08-10|2021-06-16|Telefonaktiebolaget LM Ericsson |Redundancy handling in a wireless communication network|

---

US20210266804A1|2018-08-10|2021-08-26|Lg Electronics Inc.|Method and apparatus for triggering transmission carrier reselection procedure for deactivated duplication in wireless communication system|

---

CN110839267B|2018-08-17|2022-01-28|维沃移动通信有限公司|Service node updating method, terminal equipment and network side equipment|

---

WO2020060234A1|2018-09-21|2020-03-26|주식회사 케이티|Method and device for transmitting data|

---

US20220053389A1|2018-09-27|2022-02-17|Apple Inc.|Pdcp and rohc handling for multi-connectivity handover|

---

US11070254B2|2018-09-28|2021-07-20|At&T Intellectual Property I, L.P.|Decoding data in new radio ultra-reliable low latency communications with multiple transmission points|

---

CN112970284A|2018-09-29|2021-06-15|中兴通讯股份有限公司|Ultra-reliable communication using multiple packet data unit sessions|

---

JPWO2020090442A1|2018-10-30|2021-10-07|京セラ株式会社|Wireless communication method and equipment|

---

CN111132316B|2018-10-31|2021-10-12|维沃移动通信有限公司|Resource allocation method, terminal equipment and network side equipment|

---

US20210345196A1|2018-11-01|2021-11-04|Nokia Technologies Oy|Reducing handover interruption with two transmitters and receivers|

---

US11228960B2|2018-11-12|2022-01-18|Nokia Technologies Oy|Efficient signaling in multi-connectivity scenarios|

---

CN111262648B|2018-11-30|2021-09-07|华为技术有限公司|Communication method and device|

---

CN113169901A|2018-11-30|2021-07-23|IPCom两合公司|Differential time delay measurement|

---

WO2020118519A1|2018-12-11|2020-06-18|Oppo广东移动通信有限公司|Wireless communication method, terminal device and network device|

---

WO2020120825A1|2018-12-14|2020-06-18|Nokia Technologies Oy|Packet communications|

---

WO2020141074A1|2018-12-31|2020-07-09|Telefonaktiebolaget Lm Ericsson |Handover of unacknowledged mode bearer in a wireless communication system|

---

WO2020151811A1|2019-01-22|2020-07-30|Nokia Technologies Oy|Communication apparatus, method and computer program|

---

CN111436066A|2019-02-14|2020-07-21|维沃移动通信有限公司|Data packet bearing path determination method, information sending method and equipment|

---

WO2021029801A1|2019-08-15|2021-02-18|Telefonaktiebolaget Lm Ericsson |User equipment, source access node and methods in a wireless communications network|

---

CN113596862A|2020-04-30|2021-11-02|北京三星通信技术研究有限公司|Transmission method and equipment|

---

CN111669797A|2020-05-28|2020-09-15|北京瑞华赢科技发展有限公司|Mobile network smooth switching method and device and road traffic transport vehicle|

---

US11259218B2|2020-06-29|2022-02-22|Verizon Patent And Licensing Inc.|Systems and methods for handover of dual connectivity user equipment|

法律状态:
2021-10-05| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201662402710P| true| 2016-09-30|2016-09-30|

---

US201762443152P| true| 2017-01-06|2017-01-06|

---

US201762469708P| true| 2017-03-10|2017-03-10|

---

US15/718,394|US10750410B2|2016-09-30|2017-09-28|Ultra reliable low latency connection support in radio access networks|

---

PCT/CN2017/104549|WO2018059557A1|2016-09-30|2017-09-29|Ultra reliable low latency connection support in radio access networks|

---